Dynamic network slice resolution

ABSTRACT

A first device can receive an attach request that includes information associated with a user device. The user device can provide the attach request to request access to a network. The first device can provide, to a second device and using the information associated with the user device, a request for information associated with a group identifier that is associated with the user device. The first device can receive, from the second device, the information associated with the group identifier that is associated with the user device based on providing the request for information associated with the group identifier. The first device can determine a network slice identifier that is associated with the user device based on the information associated with the group identifier that is associated with the user device. The first device can permit the user device to access a network slice, of the network, that is associated with the network slice identifier based on determining the network slice identifier.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/699,390 filed Sep. 8, 2017, which is incorporated herein byreference.

BACKGROUND

Network slicing refers to the partitioning of the same physicalinfrastructure to support different service requirements via differentnetwork slices. For example, each network slice might have separatetraffic on the user plane and the control plane, such that user trafficand control traffic on a first network slice does not interfere withuser traffic and control traffic on a second network slice. In this way,a network slice operates as a virtual network with dedicated resources(e.g., which can be adjusted dynamically) partitioned from the totalresources allocated to a base station.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, can be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2; and

FIG. 4 is a flow chart of an example process for performing dynamicnetwork slice resolution.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

Network functions virtualization (NFV) permits different network slicesto be allocated resources to handle different service requirementsassociated with different types of user devices (e.g., user equipment(UEs), Internet-of-things (IoT) devices, and/or the like) and/ordifferent applications executing on user devices. For example, differentnetwork slices might be capable of supporting different servicerequirements, such as service requirements associated with differentquality of service (QoS) levels, service requirements associated withdifferent QoS class identifier (QCI) values, service requirementsassociated with different categories of user devices, differentcombinations of QoS parameters (e.g., a latency requirement, a bandwidthrequirement, a jitter requirement, an error requirement, a reliabilityrequirement, a throughput requirement, and/or the like), and/or thelike.

As an example, a user device categorized as a smart phone can connect toa network slice associated with mobile broadband (MBB) user devices(e.g., an “MBB network slice”). MBB user devices might be associatedwith service requirements that support video streaming, multimediamessaging service (MMS), voice calls and/or voice features, servicecontinuity, charging (e.g., monitoring data usage for billing), datapath optimization, and/or the like. The MBB network slice might have adifferent resource allocation than other network slices to support theseservices, such as higher bandwidth and/or throughput to support videostreaming and/or the like.

As another example, a user device categorized as an IoT user device canconnect to a network slice associated with IoT user devices (e.g., an“IoT network slice”). IoT user devices might be associated with servicerequirements that support small data optimization, battery conservation,charging (e.g., monitoring data usage for billing), and/or the like. TheIoT network slice might have a different resource allocation than othernetwork slices to support these services, such as lower bandwidth,and/or the like.

As yet another example, a user device categorized as a mobile virtualnetwork operator (MVNO) user device might connect to a network sliceassociated with MVNO user devices (e.g., an “MVNO network slice”). MVNOuser devices might be associated with service requirements that supporta feature set of the MVNO, MBB, operator-specific charging (e.g.,monitoring data usage for billing), and/or the like. The MVNO networkslice might have a different resource allocation than other networkslices to support these services.

In a network that employs network slicing, a network slice identifiermight directly identify a particular network slice, and might beemployed to control which network slice a user device is permitted touse. A network slice identifier (e.g., a numeric slice identifier) isstored in a subscriber profile in a home subscriber server (HSS), and issent to a mobility management entity device (MME) via an Sha interface.

At attachment, a user device can request access to a particular networkslice using a network slice identifier, and the MME can use the networkslice identifier, that was received from the HSS, to validate that theuser device is permitted to access the requested network slice. If theuser device is not permitted to access the requested network slice, ordid not request a particular network slice, then the MME can redirectthe user device to another network slice based on the network sliceidentifier provided by the HSS.

Although a network slice identifier provides an unambiguous signal tothe MME regarding the appropriate network slice for a particular userdevice, usage of network slice identifiers might not provide anefficient mechanism to move existing user devices between networkslices. For example, assume that a wireless telecommunications providerdesires to create a new dedicated network slice for a set of userdevices (e.g., thousands, millions, etc. of user devices), or move theset of user devices from one network slice to another network slice. Inthis case, if the HSS stores a network slice identifier in respectivesubscriber profiles of subscribers associated with the set of userdevices, then the HSS subscriber profile for every subscriber might needto be individually modified to move the set of user devices to the newnetwork slice. Such an HSS bulk update is operationally intensive, andalso generates a large amount of signaling traffic from the HSS to theMME to inform the MME that each individual subscriber profile has beenmodified.

Some implementations described herein permit the migration of a userdevice from one network slice to another network slice by replacing anetwork slice identifier in the HSS subscriber profile with a groupidentifier that is a symbolic representation of the network sliceidentifier, and enable the MME to translate the group identifier to anetwork slice identifier.

As an example, a wireless telecommunications provider might choose toset a group identifier in an HSS subscriber profile to a company name(e.g., “Entity A”) of a company (e.g., Entity A) that is associated witha plurality of user devices. In this case, when a user device associatedwith Entity A attaches to the network, the MME can receive, from theHSS, information associated with the group identifier instead ofdirectly receiving information associated with a network sliceidentifier, and can resolve the group identifier by consulting adatabase server. The database server can store mapping information thatmaps group identifiers and network slice identifiers. In this way, theMME can resolve the group identifier to a network slice identifier.

Accordingly, some implementations described herein permit an update tothe mapping information in order to move the user devices, associatedwith the group identifier, to another (either new or existing) networkslice. Thereafter, as user devices associated with the group identifiercomplete new network attachments, the user devices can move to the othernetwork slice.

In this way, some implementations described herein enable a plurality ofuser devices to be moved from one network slice to another network slicewithout requiring the HSS to be modified for every user device of theplurality of user devices. Accordingly, implementations described hereinconserve HSS and MME processor and/or memory resources, and/or conservenetwork resources. Furthermore, implementations described hereinconserve network resources by reducing an amount of signaling traffic,from the HSS to the MME, associated with HSS subscriber profile updates.

FIGS. 1A-1C are diagrams of an overview of an example implementation 100described herein. As shown in FIG. 1A, example implementation 100 caninclude a user device, a base station, a mobility management entitydevice (MME), a home subscriber server (HSS), and a database server. Asshown by reference number 105, the user device can provide, to the basestation, a request for a connection with the base station. The MME canreceive, from the base station and based on the request from the userdevice, information associated with the user device, such as a userdevice identifier (e.g., 123456).

As further shown in FIG. 1A, and by reference number 110, the MME canprovide, to the HSS and using the information associated with the userdevice, a request for information associated with a group identifierassociated with the user device. As shown by reference number 115, theHSS can provide, to the MME and based on the request, the informationassociated with the group identifier of the user device (e.g., EntityA).

As further shown in FIG. 1A, and by reference number 120, the MME canprovide, to the database server and using the group identifier, arequest for information associated with a network slice identifierassociated with the user device. The database server can store mappinginformation that maps group identifiers and network slice identifiers.For example, as shown, the database server can store mapping informationthat maps the group identifier (e.g., Entity A) and a network sliceidentifier (e.g., network slice identifier 1). As shown by referencenumber 125, the database server can provide, to the MME, informationassociated with the network slice identifier.

As shown by reference number 130, the MME can, after determining thenetwork slice identifier, permit the user device to access a networkslice (e.g., network slice 1) identified by the network sliceidentifier. For example, the MME can provide, to the base station, aninstruction for the base station to allocate resources, that areassociated with the network slice, to the user device.

As shown in FIG. 1B, example implementation 100 can also include aclient device operated by a network operator. As shown by referencenumber 135, the client device can provide, based on input from thenetwork operator, information associated with an updated network sliceidentifier that is to be associated with the group identifier shown inFIG. 1A. For example, assume that the network operator desires to moveuser devices, that are associated with the group identifier, to adifferent network slice (e.g., network slice 4).

As shown by reference number 140, the database server can update mappinginformation, such that the updated mapping information maps the groupidentifier and the updated network slice identifier. For example, thedatabase server can be updated such that the group identifier (e.g.,Entity A) is mapped to network slice identifier 4 instead of beingmapped to network slice identifier 1.

As shown in FIG. 1C, and by reference number 145, the user device canprovide, to the base station, a request for a connection with the basestation. The MME can receive, from the base station and based on therequest from the user device, information associated with the userdevice, such as a user device identifier (e.g., 123456). As shown byreference number 150, the MME can provide, to the HSS and usinginformation associated with the user device, a request for informationassociated with a group identifier associated with the user device. Asshown by reference number 155, the HSS can provide, to the MME and basedon the request, the information associated with the group identifier ofthe user device (e.g., Entity A).

As further shown in FIG. 1C, and by reference number 160, the MME canprovide, to the database server and using the group identifier, arequest for information associated with a network slice identifierassociated with the group identifier. As shown, the database server canstore mapping information (e.g., that was updated as shown in FIG. 1B)that maps the group identifier and network slice identifier 4. As shownby reference number 165, the database server can provide, to the MME,information associated with the network slice identifier.

As shown by reference number 170, the MME can, after determining thenetwork slice identifier, permit the user device to access the networkslice identified by the network slice identifier. In this case, the MMEcan permit the user device to access network slice 4. For example, theMME can provide, to the base station, an instruction for the basestation to allocate resources, that are associated with network slice 4,to the user device.

In this way, some implementations described herein enable a plurality ofuser devices to be moved from one network slice to another network slicewithout requiring the HSS to be modified for every user device of theplurality of user devices. Accordingly, some implementations describedherein conserve MME and/or HSS processor and/or memory resourcesrelative to using a network slice identifier that is stored in the HSS.Furthermore, some implementations described herein conserve networkresources by reducing an amount of signaling traffic from the HSS to theMME associated with subscriber profile modification.

As indicated above, FIGS. 1A-1C are provided merely as an example. Otherexamples are possible and can differ from what was described with regardto FIGS. 1A-1C.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, can be implemented. As shown in FIG.2, environment 200 can include a user device 205, a base station 210, amobility management entity device (MME) 215, a serving gateway (SGW)220, a packet data network gateway (PGW) 225, a home subscriber server(HSS) 230, an authentication, authorization, and accounting server (AAA)235, a database server 240, and a network 245. Devices of environment200 can interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

Some implementations are described herein as being performed within along term evolution (LTE) network for explanatory purposes. Someimplementations can be performed within a network that is not an LTEnetwork, such as a fifth generation (5G) network, a third generation(3G) network, and/or the like.

Environment 200 can include an evolved packet system (EPS) that includesan LTE network and/or an evolved packet core (EPC) that operate based ona third generation partnership project (3GPP) wireless communicationstandard. The LTE network can include a radio access network (RAN) thatincludes one or more base stations 210 that take the form of evolvedNode Bs (eNBs) via which user device 205 communicates with the EPC. TheEPC can include MME 215, SGW 220, and/or PGW 225 that enable user device205 to communicate with network 245 and/or an Internet protocol (IP)multimedia subsystem (IMS) core. The IMS core can include HSS 230 and/orAAA 235, and can manage device registration and authentication, sessioninitiation, etc., associated with user devices 205. HSS 230 and/or AAA235 can reside in the EPC and/or the IMS core.

User device 205 includes one or more devices capable of communicatingwith base station 210 and/or a network (e.g., network 245). For example,user device 205 can include a wireless communication device, aradiotelephone, a personal communications system (PCS) terminal (e.g.,that can combine a cellular radiotelephone with data processing and datacommunications capabilities), a smart phone, a laptop computer, a tabletcomputer, a personal gaming system, and/or a similar device. User device205 can send traffic to and/or receive traffic from network 245 (e.g.,via base station 210, SGW 220, and/or PGW 225). In some implementations,user device 205 can include medical devices and/or equipment, biometricsensors and/or devices, vehicular components and/or sensors, smartmeters and/or sensors, industrial manufacturing equipment, or any othertype of device that is configured to communicate via a wireless or wiredmedium. In other words, user device 205 can include any “thing” in theIoT.

Base station 210 includes one or more devices capable of transferringtraffic, such as audio, video, text, and/or other traffic, destined forand/or received from user device 205. In some implementations, basestation 210 can include an eNB associated with the LTE network thatreceives traffic from and/or sends traffic to network 245 via SGW 220and/or PGW 225. Additionally, or alternatively, one or more basestations 210 can be associated with a RAN that is not associated withthe LTE network. Base station 210 can send traffic to and/or receivetraffic from user device 205 via an air interface. In someimplementations, base station 210 can include a small cell base station,such as a base station of a microcell, a picocell, and/or a femtocell.In some implementations, base station 210 can include an eNB, a gNB, anaccess point (AP), a new radio (NR) base station 210, a fifth generation(5G) node B, and/or the like.

MME 215 includes one or more devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with user device 205. In someimplementations, MME 215 can perform operations relating toauthentication of user device 205. Additionally, or alternatively, MME215 can facilitate the selection of a particular SGW 220 and/or aparticular PGW 225 to serve traffic to and/or from user device 205. MME215 can perform operations associated with handing off user device 205from a first base station 210 to a second base station 210 when userdevice 205 is transitioning from a first cell associated with the firstbase station 210 to a second cell associated with the second basestation 210. Additionally, or alternatively, MME 215 can select anotherMME (not pictured), to which user device 205 should be handed off (e.g.,when user device 205 moves out of range of MME 215).

SGW 220 includes one or more devices capable of routing packets. Forexample, SGW 220 can include one or more data processing and/or traffictransfer devices, such as a gateway, a router, a modem, a switch, afirewall, a network interface card (NIC), a hub, a bridge, a serverdevice, an optical add/drop multiplexer (OADM), or any other type ofdevice that processes and/or transfers traffic. In some implementations,SGW 220 can aggregate traffic received from one or more base stations210 associated with the LTE network, and can send the aggregated trafficto network 245 (e.g., via PGW 225) and/or other network devicesassociated with the EPC and/or the IMS core. SGW 220 can also receivetraffic from network 245 and/or other network devices, and can send thereceived traffic to user device 205 via base station 210. Additionally,or alternatively, SGW 220 can perform operations associated with handingoff user device 205 to and/or from an LTE network.

PGW 225 includes one or more devices capable of providing connectivityfor user device 205 to external packet data networks (e.g., other thanthe depicted EPC and/or LTE network). For example, PGW 225 can includeone or more data processing and/or traffic transfer devices, such as agateway, a router, a modem, a switch, a firewall, a NIC, a hub, abridge, a server device, an OADM, or any other type of device thatprocesses and/or transfers traffic. In some implementations, PGW 225 canaggregate traffic received from one or more SGWs 220, and can send theaggregated traffic to network 245. Additionally, or alternatively, PGW225 can receive traffic from network 245, and can send the traffic touser device 205 via SGW 220 and base station 210. PGW 225 can recorddata usage information (e.g., byte usage), and can provide the datausage information to AAA 235.

HSS 230 includes one or more devices, such as one or more serverdevices, capable of managing (e.g., receiving, generating, storing,processing, and/or providing) information associated with user device205. For example, HSS 230 can manage subscription information associatedwith user device 205, such as information associated with a subscriberprofile of a user associated with user device 205, informationassociated with services and/or applications that are accessible to userdevice 205, location information associated with user device 205, anetwork identifier (e.g., a network address) associated with user device205, information associated with a treatment of user device 205 (e.g.,quality of service information, a quantity of minutes allowed per timeperiod, a quantity of data consumption allowed per time period, etc.),and/or similar information. HSS 230 can provide this information to oneor more other devices of environment 200 to support the operationsperformed by those devices.

AAA 235 includes one or more devices, such as one or more serverdevices, that perform authentication, authorization, and/or accountingoperations for communication sessions associated with user device 205.For example, AAA 235 can perform authentication operations for userdevice 205 and/or a user of user device 205 (e.g., using one or morecredentials), can control access, by user device 205, to a serviceand/or an application (e.g., based on one or more restrictions, such astime-of-day restrictions, location restrictions, single or multipleaccess restrictions, read/write restrictions, etc.), can track resourcesconsumed by user device 205 (e.g., a quantity of voice minutes consumed,a quantity of data consumed, etc.), and/or can perform similaroperations.

Database server 240 includes one or more devices capable of receiving,processing, storing, and/or providing mapping information associatedwith group identifiers and network slice identifiers. For example,database server 240 can include a server device (e.g., a host server, aweb server, an application server, etc.), a cloud computing device, or asimilar device.

Network 245 includes one or more wired and/or wireless networks. Forexample, network 245 can include a cellular network (e.g., a 5G network,an NR network, an LTE network, a third generation (3G) network, a codedivision multiple access (CDMA) network, etc.), a public land mobilenetwork (PLMN), a wireless local area network (e.g., a Wi-Fi network), alocal area network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, and/ora combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there can be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 can beimplemented within a single device, or a single device shown in FIG. 2can be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 can perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300can correspond to user device 205, base station 210, MME 215, SGW 220,PGW 225, HSS 230, AAA 235, and/or database server 240. In someimplementations, user device 205, base station 210, MME 215, SGW 220,PGW 225, HSS 230, AAA 235, and/or database server 240 can include one ormore devices 300 and/or one or more components of device 300. As shownin FIG. 3, device 300 can include a bus 310, a processor 320, a memory330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 caninclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 caninclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 can permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 can include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 can perform one or more processes described herein. Device300 can perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 can causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 canperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for performing dynamicnetwork slice resolution. In some implementations, one or more processblocks of FIG. 4 can be performed by MME 215. In some implementations,one or more process blocks of FIG. 4 can be performed by another deviceor a group of devices separate from or including MME 215, such as userdevice 205, base station 210, SGW 220, PGW 225, HSS 230, and/or databaseserver 240.

As shown in FIG. 4, process 400 can include receiving an attach requestthat includes information associated with a user device (block 410). Forexample, MME 215 can receive an attach request from user device 205 viabase station 210.

In some implementations, user device 205 can provide an attach requestto request a connection with base station 210. For example, user device205 can transmit a radio resource control (RRC) connection requestmessage to base station 210. In some implementations, MME 215 canreceive, from base station 210, information associated with user device205 (e.g., based on an RRC connection request message, as describedabove). For example, MME 215 can receive information associated withuser device 205, such as a user device identifier, a mobile directorynumber (MDN), an international mobile subscriber identity (IMSI) number,an international mobile equipment identity (IMEI) number, a networkaddress identifier, and/or the like.

In some implementations, MME 215 can determine, based on the attachrequest, a network slice to which user device 205 is to be grantedaccess. In some implementations, a network can be associated with aplurality of network slices. Additionally, or alternatively, resourcesof the network (e.g., time resources, frequency resources,infrastructure resources, service resources, and/or the like) can beallocated to respective network slices. In some implementations, anetwork slice can also be referred to as a dedicated core network (DCN).

In some implementations, a network slice can be associated with anetwork slice identifier. For example, a first network slice (e.g.,network slice 1) can be associated with a first network slice identifier(e.g., network slice identifier 1), a second network slice (e.g.,network slice 2) can be associated with a second network sliceidentifier (e.g., network slice identifier 2), a third network slice(e.g., network slice 3) can be associated with a third network sliceidentifier (e.g., network slice identifier 3), etc. In someimplementations, a network slice identifier can be assigned to a userdevice 205 for the purpose of identifying a network slice that the userdevice 205 is to access.

In some implementations, there can be a one-to-one mapping betweennetwork slice identifiers and network slices. For example, each networkslice identifier can map to a single network slice, and each networkslice can map to a single network slice identifier. In this case, everyuser device 205 associated with a particular network slice can beassigned the same network slice identifier.

In some implementations, different network slices of the network can beassociated with different service requirements. For example, a firstnetwork slice (e.g., network slice 1) can be associated with a firstservice requirement, a second network slice (e.g., network slice 2) canbe associated with a second service requirement, a third network slice(e.g., network slice 3) can be associated with a third servicerequirement, etc.

In some implementations, a service requirement associated with a networkslice can indicate one or more network services supported by the networkslice, one or more QoS parameters guaranteed by the network slice, oneor more QCI classes supported by the network slice, a priorityassociated with traffic transmitted via the network slice (e.g., aQoS-based priority, a QCI-based priority, a priority relative to otherservice requirements of other network slices, and/or the like), one ormore user device categories supported by the network slice, and/or thelike. In some implementations, network traffic associated with a userdevice 205 assigned to a network slice identifier that is mapped to aparticular network slice can receive treatment according to the servicerequirement of that particular network slice.

In this way, MME 215 can receive the attach request, and can identifyinformation associated with user device 205 based on the attach request.Additionally, or alternatively, MME 215 can provide, to HSS 230 andusing the information associated with user device 205, a request forinformation associated with a group identifier that is associated withuser device 205, as described below. In this way, MME 215 can identify,using the group identifier, a network slice to which user device 205 isto be permitted access.

As further shown in FIG. 4, process 400 can include providing, to a homesubscriber server and using the information associated with the userdevice, a request for information associated with a group identifierthat is associated with the user device (block 420). For example, MME215 can provide, to HSS 230, a request for information associated with agroup identifier that is assigned to user device 205. In someimplementations, MME 215 can provide, to HSS 230 via an S6A interfaceand using the information associated with user device 205, a request forinformation associated with a group identifier associated with userdevice 205.

In some implementations, a group identifier can be assigned to aplurality of user devices 205, and can be used to identify a networkslice identifier and/or a network slice to which the plurality of userdevices 205 is assigned. In some implementations, there can be amany-to-one mapping between group identifiers and network sliceidentifiers. For example, multiple group identifiers can map to a singlenetwork slice identifier, and a single network slice identifier can mapto multiple group identifiers. In other words, tens, hundreds,thousands, etc. of group identifiers might map to a single network sliceidentifier. In practice, there can be thousands, millions, etc. of groupidentifiers.

In some implementations, a group identifier might not identify aparticular network slice. Put another way, and as described elsewhereherein, mapping information can map a group identifier and a networkslice identifier. The network slice identifier can directly identify theparticular network slice, whereas the group identifier can be used toidentify the network slice identifier.

In some implementations, a group identifier can be assigned to aparticular user device 205 based on attributes of user device 205, suchas an entity (e.g., a business, a company, an organization, a group ofindividuals, and/or the like) associated with user device 205, acharacteristic associated with user device 205, a service requirementassociated with user device 205, a type of user device 205, and/or thelike. As examples, a set of user devices 205 associated with aparticular entity might be associated with a first group identifier(e.g., Entity 1), another set of IoT user devices 205 can be associatedwith a second group identifier (e.g., IoT devices), and/or the like.

In some implementations, HSS 230 can store information associated with asubscriber profile based on configuration information, based on aninstruction from another device, and/or the like. In someimplementations, HSS 230 can identify a subscriber profile associatedwith user device 205 using the information associated with user device205, and can identify a group identifier associated with user device 205based on the subscriber profile. For example, HSS 230 can store, inassociation with a subscriber profile, information associated with agroup identifier that is assigned to user device 205 associated with thesubscriber profile.

In some implementations, the group identifier can remain static, whereasmapping information can be dynamically modified. In this way, HSS 230might not be required to update subscriber profile informationassociated with user device 205 in the event that user device 205 is tobe assigned to another network slice. For example, and as describedelsewhere herein, mapping information can be dynamically modified tomove user devices 205 between network slices. Thereby, someimplementations described herein conserve processor and/or memoryresources of HSS 230, and/or conserve network resources by reducing anamount of signaling associated with subscriber profile accountmodification.

In this way, MME 215 can provide, to HSS 230, the request for theinformation associated with the group identifier, and receive theinformation associated with the group identifier, as described below.

As further shown in FIG. 4, process 400 can include receiving, from thehome subscriber server, information associated with the group identifierthat is associated with the user device based on providing the request(block 430). For example, MME 215 can receive, from HSS 230 and via theS6A interface, the information associated with the group identifier ofuser device 205, and can determine, using the group identifier, anetwork slice identifier associated with user device 205, as describedbelow.

As further shown in FIG. 4, process 400 can include determining anetwork slice identifier that is associated with the user device basedon the information associated with the group identifier (block 440). Forexample, MME 215 can determine, using the group identifier, a networkslice identifier associated with user device 205.

In some implementations, database server 240 can store mappinginformation that maps a group identifier and a network slice identifier.For example, database server 240 can store information that permits agroup identifier to be resolved to a network slice identifier. In someimplementations, database server 240 can store mapping information basedon receiving the mapping information from another device, based onreceiving configuration information, and/or the like.

In some implementations, a group identifier can remain static whilemapping information can change. In this way, user devices 205 can bemoved from one network slice to another network slice without requiringbulk HSS 230 updates, without requiring a significant amount ofsignaling traffic between MME 215 and HSS 230, and/or the like. Thereby,some implementations described herein conserve processor and/or memoryresources of MME 215 and HSS 230, and/or conserve network resources.

In some implementations, MME 215 can provide, to database server 240, arequest for information associated with a network slice identifier. Forexample, MME 215 can access database server 240 and perform a lookupusing the group identifier. In this way, MME 215 can determine aparticular network slice identifier that is associated with the groupidentifier of user device 205.

Thereby, MME 215 can determine the network slice identifier associatedwith user device 205, and permit user device 205 to access a networkslice that is associated with the network slice identifier, as describedbelow.

As further shown in FIG. 4, process 400 can include permitting the userdevice to access a network slice that is associated with the networkslice identifier (block 450). For example, MME 215 can permit userdevice 205 to access a network slice, of the network, that is associatedwith the network slice identifier that is mapped to the groupidentifier.

In some implementations, MME 215 can provide an instruction to basestation 210, and can permit user device 205 to access the network slicebased on providing the instruction. For example, MME 215 can provide, tobase station 210, an instruction that causes base station 210 toallocate network resources associated with the network slice to userdevice 205, to provide treatment to network traffic associated with userdevice 205 according to the service requirements of the network slice,and/or the like.

In this way, some implementations described herein permit user device205 to be moved from one network slice to another network slice based onupdated mapping information. In other words, information associated witha subscriber profile, of user device 205, can remain static, whereas themapping information can be dynamically modified.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 can be performed in parallel.

Implementations described herein permit the migration of user devicesfrom one network slice to another network slice by replacing the networkslice identifier in the HSS profile (described above) with a groupidentifier that is a symbolic representation of the network sliceidentifier, and enable the MME to resolve the group identifier to anetwork slice identifier.

Additionally, some implementations described herein permit a databaseserver to store mapping information that maps a group identifier and anetwork slice identifier. In this way, the mapping information can beupdated to permit user devices, associated with the group identifier, tobe moved to another (either new or existing) network slice.

In this way, some implementations described herein enable a plurality ofuser devices to be moved from one network slice to another network slicewithout requiring the HSS to be modified for every user device of theplurality of user devices. Accordingly, some implementations describedherein conserve HSS and/or MME processor and/or memory resourcesrelative to using a static network slice identifier in the HSS.Furthermore, some implementations described herein conserve networkresources by reducing a quantity of signaling traffic from the HSS tothe MME associated with subscriber profile modification.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, canbe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

1. A method comprising: receiving, by a first device, an attach requestthat includes information associated with a user device, the user deviceto provide the attach request to request access to a network; providing,by the first device and to a second device and using the informationassociated with the user device, a request for information associatedwith a group identifier that is associated with the user device;receiving, by the first device and from the second device, theinformation associated with the group identifier that is associated withthe user device based on providing the request for informationassociated with the group identifier; determining, by the first device,a network slice identifier that is associated with the user device basedon the information associated with the group identifier that isassociated with the user device, where there is a many-to-one mappingbetween a plurality of group identifiers and the network sliceidentifier, and where the plurality of group identifiers includes thegroup identifier; and providing, by the first device and to a basestation, an instruction that causes the base station to allocateresources associated with a network slice, of the network, that isassociated with the network slice identifier.
 2. The method of claim 1,further comprising: permitting the user device to access the networkslice based on providing the instruction.
 3. The method of claim 1,where the instruction, that causes the base station to allocate theresources associated with the network slice, causes the base station toallocate the resources associated with the network slice to the userdevice.
 4. The method of claim 1, where the group identifier isassociated with a plurality of user devices, where the plurality of userdevices include the user device, and where the plurality of user devicesare associated with a plurality of particular attributes.
 5. (canceled)6. The method of claim 1, further comprising: providing, to a thirddevice and using the information associated with the group identifier,another request for information associated with the network sliceidentifier, where the network slice identifier is determined furtherbased on providing the other request for the information associated withthe group identifier.
 7. The method of claim 1, further comprising:permitting, without requiring a home subscriber server to be modifiedfor the user device, the user device to access another network slicethat is different from the network slice.
 8. A first device, comprising:one or more memories; and one or more processors communicatively coupledto the one or more memories, configured to: provide, to a second deviceand using information associated with a user device, a request forinformation associated with a group identifier that is associated withthe user device; receive, from the second device, the informationassociated with the group identifier based on providing the request forinformation associated with the group identifier that is associated withthe user device; determine a network slice identifier that is associatedwith the user device based on the information associated with the groupidentifier that is associated with the user device, where there is amany-to-one mapping between a plurality of group identifiers and thenetwork slice identifier, and where the plurality of group identifiersincludes the group identifier; and provide, to a base station, aninstruction that causes the base station to allocate resourcesassociated with a network slice, of a network, that is associated withthe network slice identifier.
 9. The first device of claim 8, where theone or more processors are further configured to: permit the user deviceto access the network slice based on providing the instruction.
 10. Thefirst device of claim 8, where the instruction, that causes the basestation to allocate the resources associated with the network slice,causes the base station to allocate the resources to the user device.11. (canceled)
 12. The first device of claim 8, where the one or moreprocessors are further configured to: provide, to a third device andusing the information associated with the group identifier, anotherrequest for information associated with the network slice identifier,where the network slice identifier is determined further based onproviding the other request for the information associated with thegroup identifier.
 13. The first device of claim 8, where the one or moreprocessors are further configured to: permit, without requiring a homesubscriber server to be modified for the user device, the user device toaccess another network slice that is different from a network sliceassociated with the network slice identifier.
 14. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors of a first device, cause the one or more processors to:provide, to a second device and using information associated with a userdevice, a request for information associated with a group identifier;receive, from the second device, the information associated with thegroup identifier that is associated with the user device based onproviding the request for information associated with the groupidentifier; determine a network slice identifier that is associated withthe user device based on the information associated with the groupidentifier that is associated with the user device; provide, to a basestation, an instruction that causes the base station to allocateresources associated with a network slice, of the network, that isassociated with the network slice identifier; and permit the user deviceto access another network slice that is different from a network sliceassociated with the network slice identifier.
 15. The non-transitorycomputer-readable medium of claim 14, where the one or moreinstructions, when executed by the one or more processors, further causethe one or more processors to: receive an attach request that includesthe information associated with the user device, the user device toprovide the attach request to request access to the network.
 16. Thenon-transitory computer-readable medium of claim 14, where the one ormore instructions, when executed by the one or more processors, furthercause the one or more processors to: permit the user device to accessthe network slice based on providing the instruction.
 17. Thenon-transitory computer-readable medium of claim 14, where theinstruction that causes the base station to allocate the resourcesassociated with the network slice, causes the base station to allocatethe resources to the user device.
 18. The non-transitorycomputer-readable medium of claim 14, where there is a many-to-onemapping between a plurality of group identifiers and the network sliceidentifier, and where the plurality of group identifiers include thegroup identifier.
 19. The non-transitory computer-readable medium ofclaim 14, where the one or more instructions, when executed by the oneor more processors, further cause the one or more processors to:provide, to a third device and using the information associated with thegroup identifier, another request for information associated with thenetwork slice identifier, where the network slice identifier isdetermined further based on providing the other request for theinformation associated with the group identifier.
 20. The non-transitorycomputer-readable medium of claim 14, where the one or moreinstructions, that cause the one or more processors to permit the userdevice to access the other network slice that is different from anetwork slice associated with the network slice identifier, cause theone or more processors to: permit the user device to access the othernetwork slice that is different from the network slice associated withthe network slice identifier without requiring a home subscriber serverto be modified for the user device.
 21. The method of claim 1, where theinformation associated with the user device includes at least one of: auser device identifier, a mobile directory number (MDN), aninternational mobile subscriber identity (IMSI) number, an internationalmobile equipment identity (IMEI) number, or a network addressidentifier.
 22. The first device of claim 8, where the informationassociated with the user device includes at least one of: a user deviceidentifier, a mobile directory number (MDN), an international mobilesubscriber identity (IMSI) number, an international mobile equipmentidentity (IMEI) number, or a network address identifier.